Searched hist:e888fa7bb882a1f305526d8f49d7016a7bc5f5ca (Results 1 – 1 of 1) sorted by relevance
| /linux/mm/ |
| H A D | memblock.c | diff e888fa7bb882a1f305526d8f49d7016a7bc5f5ca Wed Aug 11 10:55:18 CEST 2021 Geert Uytterhoeven <geert+renesas@glider.be> memblock: Check memory add/cap ordering
For memblock_cap_memory_range() to work properly, it should be called
after memory is detected and added to memblock with memblock_add() or
memblock_add_node(). If memblock_cap_memory_range() would be called
before memory is registered, we may silently corrupt memory later
because the crash kernel will see all memory as available.
Print a warning and bail out if ordering is not satisfied.
Suggested-by: Mike Rapoport <rppt@kernel.org>
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Link: https://lore.kernel.org/r/aabc5bad008d49f07d542815c6c8d28ec90bb09e.1628672091.git.geert+renesas@glider.be
|